home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000102_news@columbia.edu _Fri Jan 24 16:42:14 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA26345
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 24 Jan 1997 16:42:14 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id QAA28795
for kermit.misc@watsun; Fri, 24 Jan 1997 16:42:13 -0500 (EST)
Path: news.columbia.edu!panix!news-peer.gsl.net!news.gsl.net!EU.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!defsdoor.demon.co.uk!not-for-mail
From: andy@defsdoor.demon.co.uk (Andrew Porter)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Question: Overwrite existing files
Date: Fri, 24 Jan 1997 20:32:30 GMT
Lines: 26
Message-ID: <854137971.29895.0@defsdoor.demon.co.uk>
References: <01bc083d$827898a0$0c15a8c0@lm.acdis.nl>
NNTP-Posting-Host: defsdoor.demon.co.uk
X-NNTP-Posting-Host: defsdoor.demon.co.uk
X-Newsreader: Forte Agent .99b.112
Xref: news.columbia.edu comp.protocols.kermit.misc:6453
On 22 Jan 1997 08:25:10 GMT, "Luc A.M. Meijer" <lmeijer@acdis.nl>
wrote:
>I am trying to communicate from a SCO-UNIX machine via Kermit to a PC. On
>this PC is installed PROCOMM 3.0 software.
>I have the standard Host-script running on the pc and run a script on my
>SCO-system.
>Question: How can I configure PROCOMM or the script on the SCO-UNIX machine
>so that a existing file can be overwritten?
>
Well - this being a kermit newsgroup - you may not get many Procomm
experts answering this question.
However I would like to know why you use Procomm on your PC at all.
The most impressive of all the Kermits - and this is not meant to
understate how brilliant C-Kermit is - is MS-Kermit. Get it - buy the
book - use it - love it - see the movie.
To attempt to answer your question without knowing Procomm at all I
would suggest trying remote set file collision overwrite on the Unix
end, and see what happens. I would be surprised if it worked though
:)